ch: Distributed Table Engine#2997
Merged
Merged
Conversation
serprex
force-pushed
the
distributed-table-engine
branch
26 times, most recently
from
c087ec3 to
6400f05
Compare
serprex
force-pushed
the
distributed-table-engine
branch
3 times, most recently
from
d5d550e to
a1a1db1
Compare
add /{uuid} in replicated tables' path to avoid name conflicts in resync
test null table schema change
serprex
force-pushed
the
distributed-table-engine
branch
from
f475854 to
87bbb1c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
useful in conjunction with Replicated table engines
Replication is no longer stored on table mapping. Instead, peer has replicated/distributed bools. Replicated will use Replicated table engines. Specifying cluster name will adjust DDL to use
ON CLUSTER& put raw tables / destination tables behind Distributed table engineThere seems to be some issues with updates/deletes despite using
parallel_distributed_insert_select=2. But for append only use case this seems to work. Adjusting raw table's sharding key to match destination table's sharding key seems to alleviate this issue